Device and method for public land mobile network searching

ABSTRACT

This disclosure relates generally to public land mobile network searching. A device, method, and/or system may include for each of at least one mobile network identity, each mobile network identity separately associated to a different mobile network, sequentially assessing, with a processor, for each mobile network identity, identity information sets corresponding to one of the at least one mobile network identity for a location code corresponding to the mobile network associated with the one of the mobile network identities, presenting, on a user interface, information related to the mobile network corresponding to the location code as identified. Upon the location code corresponding to the mobile network having been identified, the processor ceases assessing identity information sets corresponding to the mobile network identity for the location code.

TECHNICAL FIELD

The disclosure herein relates generally to devices, systems, and/ormethods for public land mobile network searching.

BACKGROUND

The selection of a public land mobile network (PLMN) and may involveuser equipment (UE) selecting a network operator for receiving services,such as data services and/or voice services. The UE may scan apredetermined set of frequencies over the UE's band of operation, suchas all of the frequencies over the band of operation. Upon completionscanning the predetermined set of frequencies, the UE may identify alocation code corresponding to the PLMN and utilize the location code toinitiate communication with the PLMN. In various circumstances, PLMNsearching may proceed automatically, with PLMNs searched and a highestone of the PLMNs identified selected for communication. Additionally oralternatively, a list of the PLMNs as identified may be presented to auser and the user may select one of the PLMNs for obtaining service.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram a system including a UE and multiple mobilenetworks, in an example embodiment.

FIG. 2 is a hash table that may be maintained by the UE, in an exampleembodiment.

FIG. 3 is a flowchart for identifying mobile networks, in an exampleembodiment.

FIG. 4 is a flowchart for searching mobile networks, in an exampleembodiment.

FIG. 5 is a block diagram illustrating components of a machine,according to some example embodiments.

DESCRIPTION OF EMBODIMENTS

The following description and the drawings sufficiently illustratespecific embodiments to enable those skilled in the art to practicethem. Other embodiments may incorporate structural, logical, electrical,process, and other changes. Portions and features of some embodimentsmay be included in, or substituted for, those of other embodiments.Embodiments set forth in the claims encompass all available equivalentsof those claims.

A PLMN search may include the UE receiving a request from upper layers,such as a user command or high level systems or devices, to start thePLMN search. The UE may send a request for the receive signal level(RxLev) on the predetermined frequencies in the band of operation. TheUE may sort the list of frequencies in order of RxLev as determined fromthe requests. The UE may scan the list of frequencies sequentially; ifthe scan is successful the UE may decode the SI3 of that particularfrequency and either store the associated PLMN on a list or, if theprioritized PLMN has been identified, the search may be ceased.

However, such a sequence may produce circumstances where, within aspecific location, a UE may find frequencies which belong to the samePLMN. Because the UE may simply scan all of the frequencies the UE maynot be sensitive to which frequencies belong to the same PLMN. Such aprocedure may waste of time and resources.

A UE, system, and method have been developed that sequentially scanidentity information sets corresponding to mobile network identities,each mobile network identity associated with a mobile network. Eachmobile network corresponds to a location code. The identity informationsets may be scanned for a location code corresponding to the mobilenetwork associated with the mobile network identity. Upon identifyingthe location code corresponding to the mobile network, the UE may ceasesscanning the identity information sets corresponding to the mobilenetwork identity of the mobile network and moves on to the subsequentidentity information sets corresponding to a different mobile network ifthe identity information sets corresponding to any mobile networksremain unscanned.

FIG. 1 is a block diagram a system 100 including a UE 102 and multiplemobile networks 104, in an example embodiment. The UE 102 may be acellular or mobile telephone or any other device that may be configuredto communicate with a mobile network 104. The mobile networks 104 may bePLMNs or any other suitable mobile network. The mobile networks 104 maybe 2G mobile networks, 3G mobile networks, or may operate according toany of a variety of standards known in the art. The mobile networks 104may incorporate hardware and software components that allow the mobilenetworks 104 to engage in wireless communications as known in the art.

The UE 102 includes a transceiver 106 configured to transmit and receivewireless signals with the mobile networks 104 according to the protocolsof the various mobile networks 104. The transceiver 106 may beconfigured to communicate according to 2G standards, 3G standards, orany other wireless mobile network standard that has been or may bedeveloped. The capabilities and configuration of the transceiver 106 maydictate which mobile networks 104 the UE 102 may communicate with.

The UE 102 further includes a user interface 108, such as a visualdisplay, an audio input/output, and a tactile input/output, such as someor all of a touchscreen, a keyboard, and the like, and ports and/orjacks for connecting with peripheral electronic devices and/orcomponents. The UE 102 further includes a processor 110, such as amicroprocessor, a controller, or other electronic componentry configuredto perform computations or electronic processing. An electronic memory112 is configured to store electronic information and files, asdisclosed herein. The electronic memory 112 may include random accessmemory (RAM), flash memory, read only memory (ROM), a hard disk, andother forms of electronic memory and/or electronic storage known in theart.

FIG. 2 is a hash table 200 that may be maintained by the UE 102, in anexample embodiment. The hash table 200 may be accessed by the processor110 of the UE 102. The hash table 200 may be stored in the electronicmemory 112 of the UE 102 or may be stored remote to the UE 102 andaccessed remotely by the processor 110 or by another processor 110accessible by the UE 102. The processor 110 and/or the electronic memory112 may be or may be supplemented by cloud processors and/or electronicmemory.

The hash table 200 may include identity information sets includinglocation area identities (LAI) 202 as obtained by the UE 102, asdisclosed herein. Each LAI 202 may include a mobile country code (MCC),a mobile network code (MNC), and a location area code (LAC). Some or allof the LAIs 202 may include a timestamp when an immediate preceding scanwas triggered for the corresponding LAI 202. In various examples, thetimestamp may measure the time since the preceding scan in days.

Some or all of the LAIs 202 may be obtained as part of an informationbroadcasted by a mobile network 104 or a component of a mobile network104. In an example, the LAIs 202 may be transmitted as part of SystemInformation 3 (SI3) broadcasted on a broadcast control channel (BCCH)from a corresponding mobile network 104. The BCCH may carry a repeatingpattern of system information messages that identity a base transceiverstation and an absolute radio frequency channel number (ARFCN). Each LAI202, such as an LAI index, may also contain a list of nodes 204containing information about the BCCH ARFCN and cell identificationbelonging to the LAI 202. The hash table 200 is indexed by LAI 202 andmaintains, in the nodes 204 corresponding to LAI 202, the cellidentification and BCCH ARFCN for each LAI 202.

The LAIs 202 are organized in the hash table 200 according to a hashfunction, wherein Index=HashFunction(LAI). Once the SI3 is decoded for aparticular mobile network 104 belonging to a particular LAC, the BCCHARFCN and cell identification may be searched. If the BCCH ARFCN andcell identification are identified then all of the remaining BCCH ARFCNsmay be left out from scanning since such BCCH ARFCNs may belong to thesame mobile network 104 that has already been scanned and identified.The process can be repeated until all of the mobile networks 104 havebeen identified or until a prioritized or predetermined mobile network104 has been identified.

FIG. 3 is a flowchart for identifying mobile networks, in an exampleembodiment. The mobile networks may be the mobile networks 104 and maybe identified by the UE 102, or may be any other suitable mobile networkand/or may be identified by any other suitable electronic device.

At 300, a request for a mobile network list is received by theprocessor. The request may be manually generated by a user or may beautomatically generated, such as part of a communication initiationcommand or as a periodic refreshing of the mobile network list.

At 302, the UE transmits a request, such as a MPH_RXLEV_REQ, over someor all of the bands supported by the UE. At 304, the list of RxLevreceived from the request is stored, such as in the electronic memory.At 306, the list of RxLev is sorted in order of RxLev strength. At 308,it is determined if the RxLev list has been fully scanned by theprocessor. If not, at 310 a mobile network frequency is obtained from amobile network list. If so, at 312 the decoded mobile networks arepresented on a user interface of the UE and the flowchart stops at 314.

Resuming from 310, at 316, if the mobile network frequency has alreadybeen scanned then 310 is returned to and a new frequency is obtainedfrom the mobile network list. At 318, if the frequency has not alreadybeen scanned then an MPH_PLMN_SYNC_REQ is transmitted to the mobilenetwork. At 320, the UE may wait until the sync request is successful ortimes out. At 322, the SI3 provided by the mobile network is decoded andthe mobile network information to be reported to the user interface at312 is stored in the electronic memory as indexed in the hash table (ifthe mobile network information has already been indexed additionalmobile network information may not be stored or may be overwritten onthe previously stored mobile network information, in various examples).

At 324, if the LAI last scanned has a timestamp greater than a thresholdtime, then at 326 the LAI list is reset and marked for fresh scanning.Otherwise, at 328, if the LAI is marked for fresh scanning then at 330the cell identification and BCCH ARFCN are stored in the list and thetime stamp is inserted. Otherwise, at 332, if the cell identificationand the BCCH ARFCN are found on the list then at 334 all of the BCCHARFCNs in the list are read and marked as “mobile network alreadyscanned” in the RxLev list. Otherwise, at 336, the LAI list is reset.The cell identification and BCCH ARFCN are stored in the electronicmemory and the list is marked for fresh scanning. Optionally, after 330,at 338, if a priority or predetermined mobile network is identified thenthe flowchart may stop, i.e., additional mobile networks are notidentified.

FIG. 4 is a flowchart for storing radio access technology information,in an example embodiment. The flowchart may be used with respect to thesystem 100 or any other suitable network or system.

At 400, for each of at least one mobile network identity, each mobilenetwork identity separately associated to a different mobile network,identity information sets for each mobile network identity correspondingto one of the at least one mobile network identity are sequentiallyassessed for a location code corresponding to the mobile networkassociated with the one of the mobile network identities. Upon thelocation code corresponding to the mobile network having beenidentified, the processor ceases assessing identity information setscorresponding to the mobile network identity for the location code. Inan example, the identity information sets are stored as a hash table inan electronic memory. In an example, upon a location code of apredetermined priority mobile network having been identified theprocessor ceases assessing identity information sets. In an example, theinformation is an identification of the mobile network.

In an example, the identity information sets include at least some of abroadcast control channel of a mobile network, an absolute radiofrequency channel number of the mobile network, and a cellidentification for the mobile network. In an example, at least some ofthe identity information sets include a timestamp, and whereinsequentially assessing the identity information sets includessequentially assessing the identity information sets until a timestampexceeds a predetermined threshold time. In an example, the mobilenetwork identities include at least one of a mobile country code, amobile network code, and a location area code.

At 402, the sequential assessing of the identity information sets arerestarted upon identifying the timestamp that exceeds the predeterminedthreshold time. In an example, presenting includes presentinginformation pertaining to all mobile networks corresponding to locationcodes as identified.

At 404, information related to the mobile network corresponding to thelocation code as identified is caused to be presented on a userinterface.

At 406, a request is transmitted from a transceiver for at least one ofthe mobile networks to reply on a predetermined frequency supported bythe transceiver, and storing a received reply from a mobile network inan electronic memory.

FIG. 5 is a block diagram illustrating components of a machine 500,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 5 shows a diagrammatic representation of the machine500 in the example form of a computer system and within whichinstructions 524 (e.g., software) for causing the machine 500 to performany one or more of the methodologies discussed herein may be executed.In alternative embodiments, the machine 500 operates as a standalonedevice or may be connected (e.g., networked) to other machines. In anetworked deployment, the machine 500 may operate in the capacity of aserver machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 500 may be a server computer, a clientcomputer, a personal computer (PC), a tablet computer, a laptopcomputer, a netbook, a set-top box (STB), a personal digital assistant(PDA), a cellular telephone, a smartphone, a web appliance, a networkrouter, a network switch, a network bridge, or any machine capable ofexecuting the instructions 524, sequentially or otherwise, that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude a collection of machines that individually or jointly executethe instructions 524 to perform any one or more of the methodologiesdiscussed herein.

The machine 500 includes a processor 502 (e.g., a central processingunit (CPU), a graphics processing unit (GPU), a digital signal processor(DSP), an application specific integrated circuit (ASIC), aradio-frequency integrated circuit (RFIC), or any suitable combinationthereof), a main memory 504, and a static memory 506, which areconfigured to communicate with each other via a bus 508. The machine 500may further include a graphics display 510 (e.g., a plasma display panel(PDP), a light emitting diode (LED) display, a liquid crystal display(LCD), a projector, or a cathode ray tube (CRT)). The machine 500 mayalso include an alphanumeric input device 512 (e.g., a keyboard), acursor control device 514 (e.g., a mouse, a touchpad, a trackball, ajoystick, a motion sensor, or other pointing instrument), a storage unit516, a signal generation device 518 (e.g., a speaker), and a networkinterface device 520.

The storage unit 516 includes a machine-readable medium 522 on which isstored the instructions 524 (e.g., software) embodying any one or moreof the methodologies or functions described herein. The instructions 524may also reside, completely or at least partially, within the mainmemory 504, within the processor 502 (e.g., within the processor's cachememory), or both, during execution thereof by the machine 500.Accordingly, the main memory 504 and the processor 502 may be consideredas machine-readable media. The instructions 524 may be transmitted orreceived over a network 526 via the network interface device 520. Thenetwork interface device 520 may be a wired transceiver or a wirelesstransceiver, including one or more transceivers that may be utilized ina cellular or mobile network, such as the mobile network 100.

As used herein, the term “memory” refers to a machine-readable mediumable to store data temporarily or permanently and may be taken toinclude, but not be limited to, random-access memory (RAM), read-onlymemory (ROM), buffer memory, flash memory, and cache memory. While themachine-readable medium 722 is shown in an example embodiment to be asingle medium, the term “machine-readable medium” should be taken toinclude a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storeinstructions. The term “machine-readable medium” shall also be taken toinclude any medium, or combination of multiple media, that is capable ofstoring instructions (e.g., software) for execution by a machine (e.g.,machine 700), such that the instructions, when executed by one or moreprocessors of the machine (e.g., processor 702), cause the machine toperform any one or more of the methodologies described herein.Accordingly, a “machine-readable medium” refers to a single storageapparatus or device, as well as “cloud-based” storage systems or storagenetworks that include multiple storage apparatus or devices. The term“machine-readable medium” shall accordingly be taken to include, but notbe limited to, one or more data repositories in the form of asolid-state memory, an optical medium, a magnetic medium, or anysuitable combination thereof.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium or ina transmission signal) or hardware modules. A “hardware module” is atangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In various exampleembodiments, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware modules of a computer system (e.g., a processor or a groupof processors) may be configured by software (e.g., an application orapplication portion) as a hardware module that operates to performcertain operations as described herein.

In some embodiments, a hardware module may be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware module may include dedicated circuitry or logic that ispermanently configured to perform certain operations. For example, ahardware module may be a special-purpose processor, such as a fieldprogrammable gate array (FPGA) or an ASIC. A hardware module may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwaremodule may include software encompassed within a general-purposeprocessor or other programmable processor. It will be appreciated thatthe decision to implement a hardware module mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software) may be driven by cost and timeconsiderations.

Accordingly, the phrase “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. As used herein,“hardware-implemented module” refers to a hardware module. Consideringembodiments in which hardware modules are temporarily configured (e.g.,programmed), each of the hardware modules need not be configured orinstantiated at any one instance in time. For example, where a hardwaremodule comprises a general-purpose processor configured by software tobecome a special-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware modules) at different times. Software mayaccordingly configure a processor, for example, to constitute aparticular hardware module at one instance of time and to constitute adifferent hardware module at a different instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multiplehardware modules exist contemporaneously, communications may be achievedthrough signal transmission (e.g., over appropriate circuits and buses)between or among two or more of the hardware modules. In embodiments inwhich multiple hardware modules are configured or instantiated atdifferent times, communications between such hardware modules may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware modules have access.For example, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions describedherein. As used herein, “processor-implemented module” refers to ahardware module implemented using one or more processors.

Similarly, the methods described herein may be at least partiallyprocessor-implemented, a processor being an example of hardware. Forexample, at least some of the operations of a method may be performed byone or more processors or processor-implemented modules. Moreover, theone or more processors may also operate to support performance of therelevant operations in a “cloud computing” environment or as a “softwareas a service” (SaaS). For example, at least some of the operations maybe performed by a group of computers (as examples of machines includingprocessors), with these operations being accessible via a network (e.g.,the Internet) and via one or more appropriate interfaces (e.g., anapplication program interface (API)).

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the one or more processors or processor-implemented modules may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the one or more processors or processor-implemented modulesmay be distributed across a number of geographic locations.

The above detailed description includes references to the accompanyingdrawings, which form a part of the detailed description. The drawingsshow, by way of illustration, specific embodiments in which theinvention can be practiced. These embodiments are also referred toherein as “examples.” Such examples can include elements in addition tothose shown or described. However, the present inventors alsocontemplate examples in which only those elements shown or described areprovided. Moreover, the present inventors also contemplate examplesusing any combination or permutation of those elements shown ordescribed (or one or more aspects thereof), either with respect to aparticular example (or one or more aspects thereof), or with respect toother examples (or one or more aspects thereof) shown or describedherein.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In this document, the terms “including” and “inwhich” are used as the plain-English equivalents of the respective terms“comprising” and “wherein.” Also, in the following claims, the terms“including” and “comprising” are open-ended, that is, a system, device,article, composition, formulation, or process that includes elements inaddition to those listed after such a term in a claim are still deemedto fall within the scope of that claim. Moreover, in the followingclaims, the terms “first,” “second,” and “third,” etc. are used merelyas labels, and are not intended to impose numerical requirements ontheir objects.

The above description is intended to be illustrative, and notrestrictive. For example, the above-described examples (or one or moreaspects thereof) may be used in combination with each other. Otherembodiments can be used, such as by one of ordinary skill in the artupon reviewing the above description. The Abstract is provided to complywith 37 C.F.R. §1.72(b), to allow the reader to quickly ascertain thenature of the technical disclosure. It is submitted with theunderstanding that it will not be used to interpret or limit the scopeor meaning of the claims. Also, in the above Detailed Description,various features may be grouped together to streamline the disclosure.This should not be interpreted as intending that an unclaimed disclosedfeature is essential to any claim. Rather, inventive subject matter maylie in less than all features of a particular disclosed embodiment.Thus, the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separateembodiment, and it is contemplated that such embodiments can be combinedwith each other in various combinations or permutations. The scope ofthe invention should be determined with reference to the appendedclaims, along with the full scope of equivalents to which such claimsare entitled.

What is claimed is:
 1. A method, comprising: for each of at least onemobile network identity, each mobile network identity separatelyassociated with and identifying a different mobile network, sequentiallyassessing, with a processor, identity information sets corresponding toone of the at least one mobile network identity for a location codecorresponding to the mobile network associated with the one of themobile network identities; and presenting, on a user interface,information related to the mobile network corresponding to the locationcode as identified; wherein, upon the location code corresponding to themobile network having been identified, the processor ceases assessingidentity information sets corresponding to the mobile network identityfor the location code.
 2. The method of claim 1, wherein the identityinformation sets are stored as a hash table in an electronic memory. 3.The method of claim 2, wherein the identity information sets include atleast some of a broadcast control channel of a mobile network, anabsolute radio frequency channel number of the mobile network, and acell identification for the mobile network.
 4. The method of claim 2,wherein at least some of the identity information sets include atimestamp, and wherein sequentially assessing the identity informationsets includes sequentially assessing the identity information sets untila timestamp exceeds a predetermined threshold time.
 5. The method ofclaim 4, further comprising restarting the sequential assessing of theidentity information sets upon identifying the timestamp that exceedsthe predetermined threshold time.
 6. The method of claim 1, wherein themobile network identities include at least one of a mobile country code,a mobile network code, and a location area code.
 7. The method of claim1, wherein upon a location code of a predetermined priority mobilenetwork having been identified the processor ceases assessing identityinformation sets.
 8. The method of claim 1, wherein presenting includespresenting information pertaining to all mobile networks correspondingto location codes as identified.
 9. The method of claim 1, wherein theinformation is an identification of the mobile network.
 10. The methodof claim 1, further comprising transmitting, from a transceiver, arequest for at least one of the mobile networks to reply on apredetermined frequency supported by the transceiver, and storing areceived reply from a mobile network in an electronic memory.
 11. A userequipment for a mobile network, comprising: a transceiver configured toreceive identity information sets for each of at least one mobilenetwork identity, each mobile network identity separately associatedwith and identifying a different mobile network; an electronic memory,coupled to the transceiver, configured to store the identity informationsets as received by the transceiver; and a processor, coupled to theelectronic memory, configured to sequentially assess, for each mobilenetwork identity, the identity information sets for a location codecorresponding to the mobile network associated with the mobile networkidentity; wherein, upon the location code corresponding to the mobilenetwork having been identified, the processor ceases assessing identityinformation sets corresponding to the mobile network identity for thelocation code; and wherein the processor is configured to cause a userinterface to present information related to the mobile networkcorresponding to the location code as identified.
 12. The user equipmentof claim 11, wherein the identity information sets are stored as a hashtable in the electronic memory.
 13. The user equipment of claim 12,wherein the identity information sets include at least some of abroadcast control channel of a mobile network, an absolute radiofrequency channel number of the mobile network, and a cellidentification for the mobile network.
 14. The user equipment of claim12, wherein at least some of the identity information sets include atimestamp, and wherein the processor is configured to sequentiallyassess the identity information sets by, at least in part, sequentiallyassessing the identity information sets until a timestamp exceeds apredetermined threshold time.
 15. The user equipment of claim 14,wherein the processor is further configured to restart the sequentialassessing of the identity information sets upon identifying thetimestamp that exceeds the predetermined threshold time.
 16. The userequipment of claim 11, wherein the mobile network identities include atleast one of a mobile country code, a mobile network code, and alocation area code.
 17. The user equipment of claim 11, wherein upon alocation code of a predetermined priority mobile network having beenidentified the processor ceases assessing identity information sets. 18.The user equipment of claim 11, the processor is further configured tocause the user interface to present information pertaining to all mobilenetworks corresponding to location codes as identified.
 19. The userequipment of claim 11, wherein the information is an identification ofthe mobile network.
 20. The user equipment of claim 11, wherein thetransceiver is further configured to transmit a request for at least oneof the mobile networks to reply on a predetermined frequency supportedby the transceiver, and wherein the electronic memory is furtherconfigured to store a reply received from a mobile network.
 21. Themethod of claim 3, further comprising: cease assessing identityinformation sets that include an identified broadcast control channel,an identified absolute radio frequency channel number, and an identifiedcell identification for a particular mobile network.
 22. Anon-transitory computer-readable storage medium that stores instructionsfor execution by one or more processors of a user equipment (UE), theone or more processors to configure the UE to: for each of at least onemobile network identity, sequentially assess identity information setscorresponding to one of the at least one mobile network identity for alocation code corresponding to a mobile network associated with the oneof the mobile network identities, each mobile network identityseparately associated to a different mobile network; upon the locationcode corresponding to the mobile network having been identified, ceaseassessing identity information sets corresponding to the mobile networkidentity for the location code; and present information related to themobile network corresponding to the location code as identified.
 23. Themedium of claim 22, wherein the one or more processors further configurethe UE to cease assessing identity information sets that include anidentified broadcast control channel, an identified absolute radiofrequency channel number, and an identified cell identification for aparticular mobile network.
 24. The medium of claim 22, wherein: at leastsome of the identity information sets include a timestamp, and the oneor more processors further configure the UE to: sequentially assess theidentity information sets until a timestamp exceeds a predeterminedthreshold time, and restart sequential assessment of the identityinformation sets upon identifying the timestamp that exceeds thepredetermined threshold time.